Systems and methods for multi-dimensional differentiation of radio access networks

ABSTRACT

A device may receive information from a unified database, wherein the information includes a Service Profile Identifier (SPID); select a Quality-of-Service (QoS)-related identifier (ID) at least based on the SPID; and either map a radio bearer to a flow associated with a User Equipment device (UE) or configure a component to map the radio bearer to the flow. After mapping the radio bearer to the flow, the device may send data from the flow to the UE based on the QoS related ID. After configuring the component, the device may forward the SPID to a second component for sending the data from the flow to the UE based on the QoS-related ID.

BACKGROUND INFORMATION

Advanced wireless radio networks, such as Fifth Generation (5G) radioaccess networks (NG-RANs), may incorporate many new wirelesstechnologies. For example, a 5G network may allow the functions of awireless station in the NG-RAN to be split into its constituentfunctional components: a Central Unit-Control Plane (CU-CP), a CentralUnit User Plane (CU-UP), Distributed Units (DUs), and/or Radio Units(RUs). Such a split is aimed to increase flexibility in network designand to allow scalable and cost-effective network deployments. Bysplitting the functions of a wireless station, it is possible to tuneparticular performance parameters that depend on applications (e.g.,gaming application, Voice-over-IP (VoIP) application, video streamingapplication, etc.) with different latency requirements. The performanceparameters may be tuned based on the locations of the devices receivingthe service, and/or on other variables.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B illustrate concepts described herein;

FIG. 2 illustrates an example network environment in which the systemsand methods described herein may be implemented;

FIGS. 3A and 3B illustrate example functional components of a corenetwork according to different implementations;

FIG. 4 illustrates an example functional components of a wirelessstation, according to an implementation;

FIG. 5A illustrates an example network layout of Integrated Access andBackhaul (IAB) nodes according to an implementation;

FIG. 5B illustrates example functional components of IAB nodes and anIAB donor according to an implementation;

FIG. 6 is a flow diagram of an example process that is associated with5G differentiated Radio Access Network (RAN) services according to animplementation;

FIG. 7 is a diagram illustrating example signal paths and data pathsbetween example network components when providing differentiatednon-standalone (NSA) 5G RAN services, according to an implementation;

FIG. 8 is a diagram illustrating example signal paths and data pathsbetween example network components when providing differentiatedstandalone (SA) 5G RAN services, according to an implementation;

FIG. 9A illustrates example table of Service Profile Identifiers (SPIDs)for an NSA 5G RAN according to an implementation;

FIG. 9B illustrates example table of SPIDs and single-Network SliceSelection Assistance Information (NSSAIs) for an SA 5G RAN according toan implementation; and

FIG. 10 depicts components of an example network device, according to animplementation.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

The systems and methods described herein relate to differentiation ofFifth Generation (5G) Radio Access Networks (RANs) (e.g., New RadioAccess Networks (NR-RANs)) and/or Long-Tern Evolution (LTE) RANs. Inparticular, the systems and the methods described herein relate toapplying Service Profile Identifiers (SPIDs), Single-Network SliceSelection Assistance Information (S-NSSAIs), Access Control (AC)parameters, and/or Call Admission Control (CAC) parameters. The systemmay use an integrated AC and CAC database for access control and calladmission control; and use SPIDs and S-NSSAIs for assigningQuality-of-Service Class Identifiers (QCIs) and 5G QoS Identifiers(5QIs). In addition, the system may apply QCIs and/or 5QIs forscheduling data in the RANs. The system may perform all these functions,within the same wireless network, for 5G Standalone (SA) networks and/orNon-Standalone (NSA) networks. As used herein, the term SA network mayrefer to an entirely 5G network, and the term NSA network may refer to anetwork (e.g., 4G/LTE network) that includes 5G RAN components (e.g., 5Gbase station (gNB), gNB subcomponents such as Central Unit-ControlPlanes (CU-CPs), CU-User Planes (CU-UPs), Distributed Units (DUs),and/or Radio Units (RUs)). In an NSA network, the 5G RAN componentsand/or subcomponents may be anchored on LTE components, such as LTE corecomponents and/or LTE base stations (eNB).

FIG. 1A illustrates the concepts described herein, as applied to an NSAnetwork. The NSA network may be a portion of a wireless network, such asa Public Land Mobile Network (PLMN). As shown, a User Equipment device(UE) 102 connects to the NSA network that includes a RAN 204-1. RAN204-1 may comprise three different portions: portion 104-1, portion104-2, and portion 104-3. In the NSA, all portions 104 are implementedby eNB 208-2 and/or 5G RAN components DU/RU 406/408 and CU-UP 404. Thesecomponents are described below greater detail.

In portion 104-1, if UE 102 connects to eNB 208-2, eNB 208-2 may applyor enforce access control (AC) and/or UE admission control (UAC). If UE102 connects to DU 406 via RU 408, DU 406 may enforce the AC and/or UAC.The signals for causing DU 406 to enforce the AC/UAC are received by DU406 from a CU-CP (not shown).

Portion 104-2 of RAN 204-2 comprises non-5G components (e.g., eNB 208-2)and 5G RAN components (i.e., DU/RU 406/408 and CU-UP 404). If UE 102connects to RAN 204-1 via DU/RU 406/408, the data from UE 102 may bedirected to a particular CU-UP 404. The selection of a particular CU-UP404 and thus the partitioning of the RAN 104-2 into various DU/RU406/408 and CU-UP 404, may be performed upstream, at a CU-CP (not shown)based on a Service Profile Identifier (SPID). The CU-CP may also providethe SPID associated with UE 102 to DU 406 for scheduling downlink datatransmission.

In one implementation, a SPID may be a number assigned by atelecommunication service provider (e.g., a phone company). A SPID mayindicate the capabilities of UE 102 associated with the SPID. In oneimplementation, a SPID may span 14 digits that include 10 digitscorresponding to a telephone number.

In portion 104-3, depending on whether UE 102 attaches to RAN 204-2 viaeNB 208-2 or CU-UP 404, either eNB 208-2 or the CU-CP may determine theQCI corresponding to the SPID for UE 102 and forward the QCI to CU-UP404. CU-UP 404 may select or associate the radio bearer of UE 102 with aflow/stream. Thereafter, data from UE 102 to DU 406 over the radiobearer would be conveyed over the stream/flow to their destination.

FIG. 1B illustrates the concepts described herein, as applied to a SAnetwork. Like an NSA network, the SA network may also be a portion of awireless network, such as a PLMN. As shown, a UE 102 connects to the SAnetwork that includes a RAN 204-2. RAN 204-2 may comprise threedifferent portions: portion 106-1, portion 106-2, and portion 106-3. Inthe SA network, portions 106 are implemented by 5G RAN components DU/RU406/408 and CU-UP 404.

In portion 106-1, when UE 102 connects to DU/RU 406/408, DU/RU 406/408may apply or enforces access control and/or UE call admission control.DU 406 may enforce the AC and/or UAC. The signals for causing DU 406 toenforce the AC/UAC are received by DU 406 from CU-CP (not shown). ACU-CP, for example, may instruct DU/RU 406/408 to bar access to networkfor UEs 102 that attempt to access particular network slices (describedbelow).

Portion 106-2 in RAN 204-2 comprises 5G RAN components (i.e., DU/RU406/408 and CU-UP 404). If UE 102 is connected to RAN 204-2 via DU/RU406/408, the data from UE 102 may be directed to a particular CU-UP 404.The selection of a particular CU-UP 404 and thus the RAN partitioninginto various DU/RU 406/408 and CU-UP 404 may be performed upstream, at aCU-CP (not shown) based on a SPID and/or S-NSSAI. The CU-CP may obtainthe SPID associated with UE 102 from another network component andobtain S-NSSAI from UE 102, to select the CU-UP 404 for UE 102.

In portion 106-3, CU-UP 404 may associate the radio bearer of UE 102with a flow/stream that has the same 5QI. Accordingly, data from UE 102over the radio bearer would be conveyed to their destination via thestream/flow.

In both FIGS. 1A and 1B., various components of RAN 204-1 and/or RAN204-2 and other wireless network components use SPIDs, S-NSSAIs, ACparameters, and/or CAC parameters. The components may obtain AC and CACparameters from an integrated AC and CAC database (not shown) for accesscontrol and call admission control; use SPIDs and S-NSSAIs for assigningQCI and 5QI. In addition, the components may apply QCI and/or 5QI forscheduling data in the RANs. The components may perform all thesefunctions, within the same wireless network, for 5G NSA networks and/orSA networks.

FIG. 2 illustrates an example network environment 200 in which thesystems and methods described herein may be implemented. As shown,environment 200 may include UEs 102 (individually referred to as UE102), an access network 204, a core network 206, and a data network 214.UE 102 may include a wireless communication device, a mobile terminal,or a fixed wireless access (FWA) device. Examples of UE 102 include: asmart phone; a tablet device; a wearable computer device (e.g., a smartwatch); a laptop computer; an autonomous vehicle with communicationcapabilities; a portable gaming system; and an Internet-of-Thing (IoT)device.

In some implementations, UE 102 may correspond to a wirelessMachine-Type-Communication (MTC) device that communicates with otherdevices over a machine-to-machine (M2M) interface, such asLong-Term-Evolution for Machines (LTE-M) or Category M1 (CAT-M1) devicesand Narrow Band (NB)-IoT devices. UE 102 may send packets to or overaccess network 204. UE 102 may have the capability to select aparticular network slice from which UE 102 can request a service. UE 102may have the capability to connect to different Radio Access Technology(RAT) access devices, such as LTE or 5G base stations.

Access network 204 may allow UE 102 to access core network 206. To doso, access network 204 may establish and maintain, with participationfrom UE 102, an over-the-air channel with UE 102; and maintain backhaulchannels with core network 206. Access network 204 may conveyinformation through these channels, from UE 102 to core network 206 andvice versa.

Access network 204 may include an LTE radio network, a 5G radio networkand/or another advanced radio network. These radio networks may operatein many different frequency ranges, including millimeter wave (mmWave)frequencies, sub 6 GHz frequencies, and/or other frequencies. Accessnetwork 204 may include many wireless stations, CUs and DU (describedbelow with reference to FIG. 4 ) and devices herein referred to asIntegrated Access and Backhaul (IAB) nodes. In FIG. 2 , these aredepicted as a wireless station 208 and IAB nodes 210. Wireless station208 and IAB nodes 210 may establish and maintain an over-the-air channelwith UEs 102 and backhaul channels with core network 206.

Wireless station 208 may include a LTE, 5G, or another type of wirelessstation (e.g., evolved Node B (eNB), next generation Node B (gNB), etc.)that includes one or more Radio Frequency (RF) transceivers. A wirelessstation 208 that is attached to an IAB node via a backhaul link isherein referred to as IAB donor 208. As used herein, the term “IABdonor” refers to a specific type of IAB node. IAB donor 208 may have thecapability to act as a router. IAB nodes 210 may include one or moredevices to relay signals from an IAB donor to UE 102 and from UE 102 toIAB donor 208. An IAB node 210 may have an access link with UE 102 andhave a wireless and/or wireline backhaul link to other IAB nodes 210and/or IAB donor 208. An IAB node 210 may have the capability to operateas a router for other IAB nodes 210, for exchanging routing informationwith IAB donor 208 and other IAB nodes 210 and for selecting trafficpaths.

As further shown, access network 204 may include a Multi-Access EdgeComputing (MEC) cluster 212. MEC cluster 212 may be locatedgeographically close to wireless stations, and therefore also be closeto UEs 102 serviced by the wireless station. Due to its proximity to UEs102, MEC cluster 212 may be capable of providing services to UEs 102with minimal latency. Depending on the implementations, MEC cluster 212may provide many core network functions at network edges. In otherimplementations, MEC cluster 212 may be positioned at other locations(e.g., in core network 206) at which MEC cluster 212 can providecomputational resources for improved performance.

Core network 206 may include a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), an optical network, acable television network, a satellite network, a wireless network (e.g.,a Code Division Multiple Access (CDMA) network, a general packet radioservice (GPRS) network, an LTE network (e.g., a 4G network), a 5Gnetwork, an ad hoc network, a telephone network (e.g., the PublicSwitched Telephone Network (PSTN), an intranet, a PLMN, or a combinationof networks. Core network 206 may allow the delivery of InternetProtocol (IP) services to UE 102, and may interface with other networks,such as data network 214.

Depending on the implementation, core network 206 may include 4G corenetwork components (e.g., a Serving Gateway (SGW), a Packet data networkGateway (PGW), a Mobility Management Entity (MME), etc.), 5G corenetwork components (e.g., a User Plane Function (UPF), an ApplicationFunction (AF), an Access and Mobility Function (AMF), a SessionManagement Function (SMF), a Unified Data Management (UDM) function, aNetwork Slice Selection Function (NSSF), a Policy Control Function(PCF), etc.), or another type of core network components.

Data network 214 may include networks that are external to core network206. In some implementations, data network 214 may include packet datanetworks, such as an Internet Protocol (IP) network.

Although not shown, access network 204, core network 206, and datanetwork 214 may be configured to provide network slicing. Advancedwireless networks, such as a 5G network, may rely on network slicing toincrease network efficiency and performance. Network slicing involves aform of virtual network architecture that enables multiple logicalnetworks to be implemented on top of a shared physical networkinfrastructure using software defined networking (SDN) and/or networkfunction virtualization (NFV). Each logical network, referred to as a“network slice” instance, may encompass an end-to-end virtual networkwith dedicated storage and/or computational resources that includeaccess network components, clouds, transport, Central Processing Unit(CPU) cycles, memory, etc. Furthermore, each network slice instance maybe configured to meet a different set of requirements and be associatedwith a particular QoS, a type of service, and/or a particular group ofenterprise customers associated with mobile communication devices and/orfixed wireless access (FWA) devices.

Each network slice instance may be associated with an identifier, hereinreferred to as an S-NSSAI and a network slice instance ID. Each instanceof a network slice with a particular S-NSSAI may have the same S-NSSAIbut different network slice instance ID (NSI). UE 102 may connect to aparticular application in a particular network slice.

For clarity, FIG. 2 does not show all components that may be included innetwork environment 200 (e.g., routers, bridges, wireless access point,additional networks, additional UEs 102, wireless station 208, IAB nodes210, MEC clusters 212, etc.). Depending on the implementation, networkenvironment 200 may include additional, fewer, different, or a differentarrangement of components than those illustrated in FIG. 2 .Furthermore, in different implementations, the configuration of networkenvironment 200 may be different. For example, wireless station 208 maynot be linked to IAB nodes 210 and may operate in frequency ranges(e.g., sub-6 GHz) different from or same as those used by IAB nodes 210(e.g., mmWave or another frequency range).

FIG. 3A illustrates example functional components of core network 206when it is implemented as a 5G core network 206-1. In someimplementations, core network 206 may be implemented not solely as corenetwork 206-1, but as another type of core network (e.g., LTE/4G corenetwork 206-2 shown in FIG. 3B) or a combination of different types ofcore networks. As shown, 5G core network 206-1 may include corecomponents such as Access and Mobility Function (AMF) 302, a SessionManagement Function (SMF) 304, a User Plane Function (UPF) 306, a PolicyControl Function (PCF) 308, a Unified Data Management 310, and a UnifiedData Repository (UDR) 312. Depending on the implementation, core network206-1 may include additional, fewer, or different core components thanthose illustrated in FIG. 3A. Furthermore, depending on theimplementation, through network slicing and network virtualization, corecomponents 302-312 and other core components may be implemented in adata center or MEC cluster 212 in access network 204 or in data network214. In such implementations, the core components may be integrated intonetworks other than core network 206-1.

AMF 302 may perform registration management, connection management,reachability management, mobility management, lawful intercepts, ShortMessage Service (SMS) transport between UE 102 and an SMS function (notshown), session management message transport between UE 102 and SMF 304,access authentication and authorization, location services management,management of non-3GPP access networks, and/or other types of managementprocesses.

SMF 304 may perform session establishment, modification, and/or release,perform IP address allocation and management, perform Dynamic HostConfiguration Protocol (DHCP) functions, perform selection and controlof UPF 306, configure traffic steering at UPF 306 to guide traffic tothe correct destination, terminate interfaces toward PCF 308, performlawful intercepts, charge data collection, support charging interfaces,terminate session management of Non-Access Stratum (NAS) messages,perform downlink data notification, manage roaming functionality, and/orperform other types of control plane functions for managing user planedata.

UPF 306 may maintain an anchor point for intra/inter-Radio AccessTechnology (RAT) mobility, maintain an external protocol data unit (PDU)point of interconnect to a data network (e.g., data network 214),perform packet routing and forwarding, perform the user plane part ofpolicy rule enforcement, perform packet inspection, perform lawfulintercept, perform traffic usage reporting, perform QoS handling in theuser plane, perform uplink traffic verification, perform transport levelpacket marking, perform downlink packet buffering, send and forward an“end marker” to a radio access network node (e.g., gNB), and/or performother types of user plane processes.

PCF 308 may support policies to control network behavior, provide policyrules to control plane functions (e.g., to SMF 304), access subscriptioninformation relevant to policy decisions, perform policy decisions,and/or perform other types of processes associated with policyenforcement. In some implementations, PCF 308 may include a rule for anode to redirect UE 102-originated IP traffic to a selected endpoint.

UDM 310 may maintain subscription information for UEs 102, managesubscriptions, handle user identification, perform access authorizationbased on subscription data, perform network function registration orsubscription management, maintain service and/or session continuity bymaintaining assignment of SMF 304 for ongoing sessions, support SMSmessage delivery, support lawful intercept functionality, and/or performother processes associated with managing user data. UDR 312 may serve asa repository for the data that UDM 310 manages, such as user profiles.

FIG. 3B illustrates example functional components of core network 206when it is implemented as an LTE core network 206-2. In someimplementations, core network 206 may be implemented not only as anLTE/4G core network 206-2, but also as 5G core network 206-1 or acombination of different types of core networks. As shown, LTE corenetwork 206-2 may include Evolved Packet Core (EPC) components, such asa Mobility Management Entity (MME) 322, a Serving Gateway (SGW) 324, aPacket data network Gateway (PGW) 326, a Policy and Charging RulesFunction (PCRF) 328, and Home Subscriber Server (HSS) 330. The functionsof these components 322-328 roughly correspond to and are similar tothose of the functions of components 302-308, but in the context of LTEcore network. HSS 330 may roughly correspond to the functions of UDM 310and UDR 312.

FIG. 4 illustrates an example logical components 402-408 of a wirelessstation 208 when wireless station is implemented as a 5G wirelessstation (gNB) 208-1. As shown, wireless station 208-1 may include aCentral Unit-Control Plane (CU-CP) 402, a Control Unit-User Plane(CU-UP) 404, a Distributed Unit (DU) 406, and a Radio Unit (RU) 408.Depending on the implementation, the logical components of wirelessstation 208 may comprise additional, fewer, and/or different componentsthan those illustrated in FIG. 4 . For example, wireless station 208-1may include multiple DUs 406 and RUs 408. Furthermore, althoughcomponents 402-408 are depicted as being included in wireless station208-1, each of components 402-408 may be implemented in access network204 without being confined to a specific wireless station 208-1.Furthermore, CU-CP 402 and CU-UP 404 may be implemented in MEC cluster212 or in a data center as part of a network slice through networkfunction virtualization.

CU-CP 402 may perform control plane signaling associated with managingDU 406 over F1-C interface 410. CU-CP 402 may signal to DU 406 over acontrol plane communication protocol stack that includes, for example,F1AP (e.g., the signaling protocol for F1 interface between a CU and aDU). CU-CP 402 may include protocol layers comprising: Radio ResourceControl (RRC) layer and a Packet Data Convergence Protocol-Control Plane(PDCP-C). DU 406 may include corresponding stacks to handle/respond tothe signaling (not shown).

CU-UP 404 may perform user plane functions associated with managing DU406 over F1-U interface 412. CU-UP 404 may interact with DU 406 over auser plane communication protocol stack that includes, for example,General Packet Radio Service Tunneling Protocol (GTP)-User plane, theUser Datagram Protocol (UDP), and the IP. DU 406 would havecorresponding layers to handle/respond to messages from CU-UP 404 (notshown). CP-UP 404 may include processing layers that comprise a ServiceData Adaptation Protocol (SDAP) and a PDCP-User Plane (PDCP-U). CU-UP404 and CU-CP 402 communicate over E1 interface 414, for example, forexchanging bearer setup messages.

Although CU-CP 402 and CU-UP 404 (collectively referred to as CU) and DU406 are illustrated as part of wireless station 208, the CU-CP 402,CU-UP 404, and DU 406 do not need to be physically located close to oneanother, as CU-CP 402 and CU-UP 404 may be implemented as cloudcomputing elements, through network function virtualization capabilitiesof the cloud. A CU may communicate with the components of core network206 through S1/NG interfaces and with other CUs through X2/Xninterfaces.

DU 406 may provide support for one or more cells covered by radio beamsat the RU 408. DU 406 may handle UE mobility, from a DU to a DU, gNB togNB, cell to cell, beam to beam, etc. RU 408 may perform physical layerfunctions, such as antenna functions, transmissions of radio beams, etc.

FIG. 5A illustrates an example network layout of IAB nodes 210. Asshown, some IAB nodes 210 may be attached to wireless station 208 (e.g.,gNB), otherwise referred to as IAB donor 208 and to other IAB nodes 210through backhaul links. Each IAB node 210 may have a parent nodeupstream (e.g., either a parent IAB node 210 or IAB donor 208) and achild node downstream (e.g., either a UE 102 or a child IAB node 210).An IAB node 210 that has no child IAB node 210 is herein referred to asa leaf IAB node 210. UE 102 may establish an access link with any of IABnodes 210 and not just leaf IAB nodes 210.

FIG. 5B illustrates example functional components of IAB donor 208 andIAB nodes 210 in FIGS. 2 and 5A. In FIG. 5B, although only a single IABnode 210-1 is shown to be between IAB node 210-2 and IAB donor 208, inother embodiments, there may be many IAB nodes 210 between an IAB node210-2 and IAB donor 208. Furthermore, although, FIG. 5B shows only asingle path from IAB node 210-2 to IAB donor 208, there may be one ormore paths from IAB node 210-2 to IAB donor 208. As shown, IAB donor 208includes CU-CP 402, CU-UP 404, and DU 406-D; IAB node 210-1 includesmobile terminal (MT) 502-1 and DU 406-1; and IAB node 210-2 includes MT502-2 and DU 406-2.

In FIG. 5B, the control plane connections from CU-CP 402 and CU-UP 404in IAB donor/wireless station 208 are shown as terminating at DU 406-2in IAB node 114-2. However, for the path between IAB donor 208 and IABnode 210-1, CU-CP 402 and CU-UP 404 would terminate their connections atDU 406-1 in IAB node 210-1, although not shown in FIG. 5B.

Each of MTs 502-1 and 502-2 permits its host device to act like a mobileterminal (e.g., UE 102). For example, to DU 406-D in IAB donor 208, MT502-1 in IAB node 210-1 behaves similarly as a mobile terminalwirelessly attached to DU 406-D. The relationship between MT 502-1 andDU 406-D, and between MT 502-2 and DU 406-1, is established over aBackhaul (BH) channel 504-1 between DU 406-D of IAB donor 208 and MT502-1 of IAB node 210-1 and over BH channel 504-2 between DU 406-1 ofIAB node 210-1 and MT 502-2 of IAB node 210-2.

Each of BH channels 504-1 and 504-2 in FIG. 5B includes multiple networklayers that comprise, for example, a Backhaul Adaptation Layer (BAP), aRadio Link Control (RLC), a Media Access Control (MAC), and a Physicallayer (PHY. These layers are not illustrated in FIG. 5B.

As BH channels may be RF channels, IAB nodes 210 may be part of accessnetwork 204 through wireless connections and therefore do not need to beinterconnected through cables or optical fibers. In contrast to otherwireless stations that are bound to access network 204 through cables oroptical fibers, IAB nodes 210 may be placed in locations where cables orfibers are difficult to lay, and therefore, may easily provide accesspoints for UEs 102. If necessary, IAB nodes 210 may be moved from onegeographical location to another without re-cabling, as communicationdemands at different locations change.

FIG. 6 is a flow diagram of an example process 600 that is associatedwith differentiated 5G RAN services according to an implementation.Below, process 600 is described along with reference to FIGS. 7 and 8 .FIG. 7 is a diagram illustrating example signal paths and data pathsbetween example network components, of the system described herein, whenproviding differentiated SA 5G RAN services. Although not shown, UE102-2 may attach not only directly to gNB 208-1, but through an IAB node210 that is one or more hops away from gNB 208-1 (see FIG. 5A). FIG. 8is a diagram illustrating example signal paths and data paths betweenexample network components, of the system described herein, whenproviding differentiated NSA 5G RAN services. Although not shown, DU 406may be part of an IAB node 210 that is one or more hops from CU-CP 402(see FIG. 5A).

Process 600 may be performed by one or more of the components shown inFIGS. 7 and 8 . As shown, process 600 may include obtaining informationabout AC or CAC from a Unified Database (UDB) (block 602). For example,in FIG. 7 , eNB 208-2 may receive AC/CAC information from UDB 750 overpaths 702 and 704, and gNB 208-1 may receive the same information viaeNB 208-2. In one embodiment, UDB 750 may be implemented by HSS 330. Inanother example, in FIG. 8 , CU-CP 402 may receive AC/CAC informationfrom UDB 850 over path 802 and 806. In one embodiment, UDB 850 may beimplemented by UDM 310.

Process 600 may include performing access control (block 604). Forexample, in FIG. 7 , eNB 208-2 and/or gNB 208-1 may broadcast signalsfor access barring. UEs 102 that meet the conditions specified in theaccess barring signals may refrain from attaching to eNB 208-2 and/orgNB 208-1. In another example, in FIG. 8 , CU-CP 402 may instruct DUs406 to broadcast access barring signals via RU 408 (not shown in FIG. 8). In response to the instruction from CU-CP 402, DU 406 may broadcastaccess barring signals to UEs 102. UEs 102 that meet the conditionsspecified in the access barring signals may refrain from attaching to DU406 (e.g., UE 102 which to access particular network slices may bebarred).

Process 600 may further include performing call admission control (block606). With reference to FIG. 7 , continuing with the preceding example,assumed that eNB 208-2 or gNB 208-1 is accessible to UE 102-1 or 102-2.UE 102-1 or UE 102-2 may attempt to establish a link with eNB 208-2 orgNB 208-1 and register with core network 206. During the attempt, eNB208-2 or gNB 208-1 may determine whether the connection is admissiblebased on the current bandwidth use, the number of connections eNB 208-2or gNB 208-1 has with other UEs 102, etc. In some implementations, eNB208-2 or gNB 208-1 may have received the thresholds for determining thecall admissions from UDB 750 (e.g., at block 602). If permitting UE102-1 or 102-2 to connect to gNB 208-1 or eNB 208-2 would cause eNB208-2 or gNB 208-1 to exceed the bandwidth use threshold or thethreshold number of connections to other UEs 102, etc., gNB 208-1/eNB2080-2 would not allow UE 102-2 or 102-1 to establish a Radio ResourceControl (RRC) connection with gNB 208-1 or eNB 208-2 and register withcore network 206. Similarly, in FIG. 8 , continuing with the precedingexample, assume that DU 406 is accessible to UE 102, UE 102 may attemptto establish a link with DU 406. During the attempt, DU 406 maydetermine whether the connection is admissible based on its currentbandwidth use, the number of connections that DU 406 has with other UEs102, etc. If determined to be admissible, DU 406 would allow UE 102 toestablish an RRC connection with DU 406 and register with core network206. Otherwise, DU 406 would not allow UE 102 to establish theconnection and register.

Process 600 may further include wireless station 208 or CU-CP 402/DU406determining whether the RAN component that handles the signals from UE102 is an eNB (block 608). If the RAN component is an eNB (block 608:YES), process 600 may proceed to block 610.

At block 610, eNB 208-2 may apply LTE RAN partitioning. That is RANcomponents may operate as LTE components. Furthermore, eNB 208-2 and gNB208-2 may schedule data to/from UE 102-1 or UE 102-2 based SPIDs andQCIs (block 612). For example, continuing with the preceding exampleassociated with FIG. 7 , assume that UE 102-1 establishes an RRCconnection with eNB 208-2 and registers with core network 206 via eNB208-2, MME 322, UDB 750, etc. After the registration, when eNB 208-2receives a request to establish a session from UE 102-1, eNB 208-1 mayobtain parameters of the request (e.g., an Access Point Name, anapplication ID, an International Mobile Subscriber Identity (IMSI),etc.) and forward a session modification message including theparameters to MME 322 over path 704. MME 322 may consult UDB 750 forsubscriber information as needed, select a SGW 324 if needed, and signalthe selected SGW 324 via path 706, relaying any of the informationneeded to establish an anchor point for the UE session. SGW 324 may thensignal PGW 326 over path 708, to have PGW 326 provide the anchor point.

Assuming that the anchor point setup is successful, MME 322 may thensend a reply to eNB 208-2, providing information that MME 322 obtainedfrom UE 102-1, such as Service Profile Identifier (SPID). When eNB 208-2receives the information from MME 322, eNB 208-2 may map the SPID to aQCI (Quality-of-Service (QoS) Class Identifier). In addition, eNB 208-2may assign the radio bearer for UE 102-1 to a flow associated with theanchor point at PGW 326. Thereafter, when eNB 208-2 receives data for UE102-1 from the anchor point, eNB 208-2 may schedule the data fortransmission to UE 102-1, in accordance with the QCI. For example, ifeNB 208-2 has connections to multiple UEs 102 and each UE 102 hasestablished a session, eNB 208-2 may receive many streams of data fromdifferent anchor points for UEs 102. eNB 208-2 may schedule data fromdifferent flows/streams in accordance with the QCIs associated with eachflow/stream, for transmission to the UEs 102.

Returning to block 608, if the RAN component is not eNB 208-2 (block608: NO), process 600 may proceed to block 614. At block 614, gNB 208-1(since the device has determined that it is not an eNB, it has to be agNB) may apply 5G RAN partitioning. That is RAN components operate as 5GRAN components. Furthermore, DU 406 may schedule data to/from UE 102based on S-NSSAIs, SPIDs, and 5QIs (block 616). For example, continuingwith the preceding example associated with FIG. 8 , assume that UE 102establishes an RRC connection with DU 406 and registers with corenetwork 206 via DU 406, CU-CP 402, AMF 302, UDB 850, etc. After theregistration, when DU 406 receives a request to establish a session fromUE 102, DU 406 may obtain parameters of the request (e.g., an S-NSSAI,an application ID, an IMSI, an External ID, an identifier for the dataradio bearer (DRB ID), etc.) and forward a UE context message includingthe parameters to CU-CP 402 over path 804. CU-CP 402 may then send asession modification request including some or all of the parameters toAMF 302 (path 806).

When AMF 302 receives the request for session from CU-CP 402, inresponse, AMF 302 may request, over path 808, SMF 304 to create ormodify a session. Upon receipt of the message, SMF 304 may select a UPF306 based on information about the endpoint with which UE 102 is toestablish the session. SMF 304 may exchange signals with UPF 306 overpath 810 to set an anchor point at UPF 306. SMF 304 then messages AMF302 about the anchor point and UPF 306 over path 808.

After AMF 302 receives the message from SMF 304, AMF 302 may informCU-CP 402 over path 806, that the anchor point is established. Dependingon the implementation, CU-CP 402 may then select CU-UP 404 based on alist of available CU-CPs 404. For example, CU-CP 402 may select theCU-UP 404 that is able to handle the required bandwidth for UE 102. Inother implementations, a default CU-UP 404-1 that is associated with theUPF 306 may be selected. After selecting CU-UP 404, CU-CP 402 may send abearer context message over path 812 so that the selected CU-UP 404 canmap the DRB at DU 406 to a particular flow path 816. Once the mapping iscomplete, the requested session can be established from UE 102 to theendpoint via UPF 306. Thereafter, CU-UP 404 can receive session datafrom DU 406 over path 814 (F1-U) and forward the data to UPF 306, overpath 816. CU-UP 404 may also forward session data received from UPF 306to DU 406. DU 406 may forward any uplink data to CU-UP 404 and downlinkdata to UE 102.

In addition to configuring CU-UP 304, CU-CP 302 may provide informationto DU 406 so that DU 406 can schedule data to and from UE 102. Forexample, CU-CP 302 may provide the SPID and/or 5QI to DU 406. DU 406 maythen use the SPID, S-NSSAI, and/or 5QI to schedule data for transmissionto UE 102.

FIG. 9A illustrates example table of SPIDs for an NSA 5G RAN accordingto an implementation. With reference to FIG. 7 , as described above,when eNB 208-1 receives information about UE 102-2 or gNB 208-1 obtainsinformation about UE 102-1, eNB 208-2 or gNB 208-1 may receive a SPID.eNB 208-2 or gNB 208-1 may use the SPID to determine a correspondingQCI. Table 900 shows one possible mapping between different SPIDs andQCIs. For example, SPID_MEC, SPID_FWA, and SPID_EMBB may correspond toQCI_A, QCI_B, and QCI_C. SPID_MEC, SPID_FWA, and SPID_EMBB are serviceprofile identifiers for services related to a MEC, a fixed wirelessaccess point, and an enhanced mobile broadband service. QCI_A, QCI_B,and QCI_C may correspond to different quality of service based onlatencies (e.g., latency <30 milliseconds).

FIG. 9B illustrates example tables of SPIDs and single-Network SliceSelection Assistance Information (NSSAIs) for a 5G NR network accordingto an implementation. With reference to FIG. 8 , as described above,when DU 406 receives information about UE 102 for scheduling, DU 406 mayreceive a SPID and/or S-NSSAI associated with UE 102. DU 406 may use theSPID or S-NSSAI to determine a corresponding QCI or 5QI. In oneimplementation, DU 406 may use the mapping shown by tables 904 and 906to determine its own 5QI.

Table 902 shows one possible mapping between different SPIDs and QCIsfor an SA network. For example, SPID MEC and SPID MEC1 may correspond toQCI_A (latency <30 milliseconds) and QCI_B (latency <20 milliseconds).Table 904 shows one possible mapping between different S-NSSAIs and 5QIsfor an SA network. For example, S-NSSAI1, S-NSSAI2, and S-NSSAI3 maycorrespond to 5QI_1 (latency <30 milliseconds), 5QI_4 (latency <20milliseconds), and 5QI_5 (latency <10 milliseconds).

FIG. 10 depicts example components of an example network device 1000.Network device 1000 corresponds to or is included in UE 102, IAB nodes210, and any of the network components of FIGS. 1-5, 7, and 8 (e.g., arouter, a network switch, servers, gateways, gNB 208-1, eNB 208-2, MECcluster 212, AMF 302, SFM 304, UPF 306, PCF 308, UDM 310, UDR 312, MME322, SGW 324, PGW 326, PCRF 328, HSS 330, CU-CP 402, CU-UP 404, DU 406,etc.). As shown, network device 1000 includes a processor 1002,memory/storage 1004, input component 1006, output component 1008,network interface 1010, and communication path 1012. In differentimplementations, network device 1000 may include additional, fewer,different, or a different arrangement of components than the onesillustrated in FIG. 10 . For example, network device 1000 may include adisplay, network card, etc.

Processor 1002 may include a processor, a microprocessor, an ApplicationSpecific Integrated Circuit (ASIC), a Field Programmable Gate Array(FPGA), a programmable logic device, a chipset, an application specificinstruction-set processor (ASIP), a system-on-chip (SoC), a centralprocessing unit (CPU) (e.g., one or multiple cores), a microcontroller,and/or another processing logic device (e.g., embedded device) capableof controlling network device 1000 and/or executingprograms/instructions.

Memory/storage 1004 may include static memory, such as read only memory(ROM), and/or dynamic memory, such as random access memory (RAM), oronboard cache, for storing data and machine-readable instructions (e.g.,programs, scripts, etc.).

Memory/storage 1004 may also include a CD ROM, CD read/write (R/W) disk,optical disk, magnetic disk, solid state disk, holographic versatiledisk (HVD), digital versatile disk (DVD), and/or flash memory, as wellas other types of storage device (e.g., Micro-Electromechanical system(MEMS)-based storage medium) for storing data and/or machine-readableinstructions (e.g., a program, script, etc.). Memory/storage 1004 may beexternal to and/or removable from network device 1000. Memory/storage1004 may include, for example, a Universal Serial Bus (USB) memorystick, a dongle, a hard disk, off-line storage, a Blu-Ray® disk (BD),etc. Memory/storage 1004 may also include devices that can function bothas a RAM-like component or persistent storage, such as Intel® Optanememories.

Depending on the context, the term “memory,” “storage,” “storagedevice,” “storage unit,” and/or “medium” may be used interchangeably.For example, a “computer-readable storage device” or “computer-readablemedium” may refer to both a memory and/or storage device.

Input component 1006 and output component 1008 may provide input andoutput from/to a user to/from network device 1000. Input and outputcomponents 1006 and 1008 may include, for example, a display screen, akeyboard, a mouse, a speaker, actuators, sensors, gyroscope,accelerometer, a microphone, a camera, a DVD reader, Universal SerialBus (USB) lines, and/or other types of components for obtaining, fromphysical events or phenomena, to and/or from signals that pertain tonetwork device 1000.

Network interface 1010 may include a transceiver (e.g., a transmitterand a receiver) for network device 1000 to communicate with otherdevices and/or systems. For example, via network interface 1010, networkdevice 1000 may communicate with wireless station 208.

Network interface 1010 may include an Ethernet interface to a LAN,and/or an interface/connection for connecting network device 1000 toother devices (e.g., a Bluetooth interface). For example, networkinterface 1010 may include a wireless modem for modulation anddemodulation.

Communication path 1012 may enable components of network device 1000 tocommunicate with one another.

Network device 1000 may perform the operations described herein inresponse to processor 1002 executing software instructions stored in anon-transient computer-readable medium, such as memory/storage 1004. Thesoftware instructions may be read into memory/storage 1004 from anothercomputer-readable medium or from another device via network interface1010. The software instructions stored in memory or storage (e.g.,memory/storage 1004, when executed by processor 1002, may causeprocessor 1002 to perform processes that are described herein. Forexample, UE 102, AMF 302, SMF 304, UPF 306, wireless station/IAB donor208, IAB nodes 210, CU-CP 402, CU-UP 404, and DU 406 may each includevarious programs for performing some of the above-described functionsand processes.

In this specification, various preferred embodiments have been describedwith reference to the accompanying drawings. Modifications may be madethereto, and additional embodiments may be implemented, withoutdeparting from the broader scope of the invention as set forth in theclaims that follow. The specification and drawings are accordingly to beregarded in an illustrative rather than restrictive sense.

While a series of blocks have been described above with regard to theprocess illustrated in FIG. 6 , the order of the blocks may be modifiedin other implementations. In addition, non-dependent blocks mayrepresent blocks that can be performed in parallel.

It will be apparent that aspects described herein may be implemented inmany different forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement aspects does not limitthe invention. Thus, the operation and behavior of the aspects weredescribed without reference to the specific software code—it beingunderstood that software and control hardware can be designed toimplement the aspects based on the description herein.

Further, certain portions of the implementations have been described as“logic” that performs one or more functions. This logic may includehardware, such as a processor, a microprocessor, an application specificintegrated circuit, or a field programmable gate array, software, or acombination of hardware and software.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be collected, stored, and used in accordancewith all applicable laws concerning protection of personal information.The collection, storage and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, block, or instruction used in the present application shouldbe construed as critical or essential to the implementations describedherein unless explicitly described as such. Also, as used herein, thearticles “a,” “an,” and “the” are intended to include one or more items.Further, the phrase “based on” is intended to mean “based, at least inpart, on” unless explicitly stated otherwise.

What is claimed is:
 1. A component comprising: a processor configuredto: receive information from a unified database, wherein the informationincludes a Service Profile Identifier (SPID); select aQuality-of-Service (QoS)-related identifier (ID) at least based on theSPID; either map a radio bearer to a flow associated with a UserEquipment device (UE) or configure a second component to map the radiobearer to the flow; and after the processor maps the radio bearer to theflow, send data from the flow to the UE based on the QoS related ID; orafter the second component is configured, forward the SPID to a thirdcomponent that sends the data from the flow to the UE based on theQoS-related ID.
 2. The component of claim 1, wherein the componentincludes one of an evolved Node B (eNB) or a Central Unit-Control Plane(CU-CP).
 3. The component of claim 1, wherein the second componentincludes a Central Unit-User Plane (CU-CP) and the third componentincludes a Distributed Unit (DU).
 4. The component of claim 1, whereinthe QoS-related ID includes: a QoS Class ID (QCI) or a Fifth GenerationQoS ID (5QI)
 5. The component of claim 1, wherein one of the processoror the third component is further configured to: apply access controland call admission control.
 6. The component of claim 5, wherein whenone of the processor or the third component applies access control, oneof the processor or the third component is configured to: broadcastaccess barring information to UEs.
 7. The component of claim 1, whereinwhen the processor selects the QoS-related ID, the processor selects theQoS-related ID based on the SPID and a Single-Network Slice SelectionAssistance Information (S-NSSAI).
 8. The component of claim 1, whereinwhen the processor sends the data from the flow to the UE based on theQoS-related ID, the processor is configured to: schedule the data fortransmission based on the QoS-related ID; and transmit the data to theUE in accordance with the scheduling.
 9. The component of claim 1,wherein the third component includes one or more Integrated Access andBackhaul (IAB) nodes.
 10. The component of claim 1, wherein the unifieddatabase includes one of: a Home Subscriber Server or a Unified DataManagement (UDM).
 11. A method comprising: receiving information from aunified database, wherein the information includes a Service ProfileIdentifier (SPID); selecting a Quality-of-Service (QoS)-relatedidentifier (ID) at least based on the SPID; either mapping a radiobearer to a flow associated with a User Equipment device (UE) orconfiguring a component to map the radio bearer to the flow; and aftermapping the radio bearer to the flow, sending data from the flow to theUE based on the QoS related ID; or after configuring the secondcomponent, forwarding the SPID to a second component for sending thedata from the flow to the UE based on the QoS-related ID.
 12. The methodof claim 11, wherein receiving includes: receiving, at either an evolvedNode B (eNB) or a Central Unit-Control Plane (CU-CP), the informationfrom the unified database.
 13. The method of claim 11, wherein thecomponent includes a Central Unit-User Plane (CU-CP) and the secondcomponent includes a Distributed Unit (DU).
 14. The method of claim 11,wherein the OoS-related ID includes: a QoS Class ID (QCI) or a FifthGeneration QoS ID (5QI)
 15. The method of claim 11, further comprising:applying access control and call admission control.
 16. The method ofclaim 15, wherein applying access control includes: broadcasting accessbarring information to UEs.
 17. The method of claim 11, whereinselecting the QoS-related ID includes: selecting the QoS-related IDbased on the SPID and a Single-Network Slice Selection AssistanceInformation (S-NSSAI).
 18. The method of claim 11, wherein sending thedata from the flow to the UE based on the QoS-related ID includes:scheduling the data based on the QoS-related ID; and transmitting thedata to the UE.
 19. A non-transitory computer-readable medium comprisingprocessor-executable instructions, wherein when executed by a processor,the instructions cause the processor to: receive information from aunified database, wherein the information includes a Service ProfileIdentifier (SPID); select a Quality-of-Service (QoS)-related identifier(ID) at least based on the SPID; either map a radio bearer to a flowassociated with a User Equipment device (UE) or configure a component tomap the radio bearer to the flow; after mapping the radio bearer to theflow, send data from the flow to the UE based on the QoS related ID; orafter configuring the second component, forward the SPID to a secondcomponent for sending the data from the flow to the UE based on theQoS-related ID.
 20. The non-transitory computer readable medium of claim19, wherein the second component includes one or more Integrated Accessand Backhaul (IAB) nodes.